0.0
NA
CVE-2026-32283
Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
Description

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

INFO

Published Date :

April 8, 2026, 2:16 a.m.

Last Modified :

April 8, 2026, 2:16 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-32283 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Update TLS 1.3 implementation to properly handle multiple key update messages.
  • Apply vendor-provided patches for TLS 1.3.
  • Ensure TLS 1.3 handles key updates correctly.
  • Monitor resource consumption on TLS connections.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-32283.

URL Resource
https://go.dev/cl/763767
https://go.dev/issue/78334
https://groups.google.com/g/golang-announce/c/0uYbvbPZRWU
https://pkg.go.dev/vuln/GO-2026-4870
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-32283 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-32283 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-32283 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-32283 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Apr. 08, 2026

    Action Type Old Value New Value
    Added Description If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
    Added Reference https://go.dev/cl/763767
    Added Reference https://go.dev/issue/78334
    Added Reference https://groups.google.com/g/golang-announce/c/0uYbvbPZRWU
    Added Reference https://pkg.go.dev/vuln/GO-2026-4870
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.